<rdf:RDF
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 xmlns="http://purl.org/rss/1.0/"
 xmlns:dc="http://purl.org/dc/elements/1.1/"
 xmlns:cc="http://web.resource.org/cc/"
 >
<!--
	This ontology document is licensed under the Creative Commons
	Attribution License. To view a copy of this license, visit
	http://creativecommons.org/licenses/by/2.0/ or send a letter to
	Creative Commons, 559 Nathan Abbott Way, Stanford, California
	94305, USA.
-->
 <channel rdf:about="http://ebiquity.umbc.edu//tag/html/named entities/?t=named+entities">
  <cc:license rdf:resource="http://creativecommons.org/licenses/by/2.0/" />
  <title><![CDATA[UMBC ebiquity RSS Tag Search]]></title>
  <link><![CDATA[http://ebiquity.umbc.edu//tag/html/named entities/?t=named+entities]]></link>
  <description><![CDATA[UMBC ebiquity RSS Tag Search for named entities]]></description>
  <items>
    <rdf:Seq>
      <rdf:li resource="http://ebiquity.umbc.edu/event/html/id/480/Beyond-NER-Towards-Semantics-in-Clinical-Text"/>
      <rdf:li resource="http://ebiquity.umbc.edu/paper/html/id/716/Beyond-NER-Towards-Semantics-in-Clinical-Text"/>
      <rdf:li resource="http://ebiquity.umbc.edu/paper/html/id/476/Annotating-named-entities-in-Twitter-data-with-crowdsourcing"/>
    </rdf:Seq>
  </items>
 </channel>
 <item rdf:about="http://ebiquity.umbc.edu/event/html/id/480/Beyond-NER-Towards-Semantics-in-Clinical-Text">
  <title><![CDATA[Beyond NER: Towards Semantics in Clinical Text]]></title>
  <link>http://ebiquity.umbc.edu/event/html/id/480/Beyond-NER-Towards-Semantics-in-Clinical-Text</link>
  <description><![CDATA[While clinical text NLP systems have become very effective in recognizing named entities in clinical text and mapping them to standardized terminologies in the normalization process, there remains a gap in the ability of extractors to combine entities together into a complete semantic representation of medical concepts that contain multiple attributes each of which has its own set of allowed named entities or values. Furthermore, additional domain knowledge may be required to determine the se...]]></description>
  <dc:date>2015-10-05</dc:date>
 </item>
 <item rdf:about="http://ebiquity.umbc.edu/paper/html/id/716/Beyond-NER-Towards-Semantics-in-Clinical-Text">
  <title><![CDATA[Beyond NER: Towards Semantics in Clinical Text]]></title>
  <link>http://ebiquity.umbc.edu/paper/html/id/716/Beyond-NER-Towards-Semantics-in-Clinical-Text</link>
  <description><![CDATA[While clinical text NLP systems have become very effective in recognizing named entities in clinical text and mapping them to standardized terminologies in the normalization process, there remains a gap in the ability of extractors to combine entities together into a complete semantic representation of medical concepts that contain multiple attributes each of which has its own set of allowed named entities or values. Furthermore, additional domain knowledge may be required to determine the se...]]></description>
  <dc:date>2015-10-11</dc:date>
 </item>
 <item rdf:about="http://ebiquity.umbc.edu/paper/html/id/476/Annotating-named-entities-in-Twitter-data-with-crowdsourcing">
  <title><![CDATA[Annotating named entities in Twitter data with crowdsourcing]]></title>
  <link>http://ebiquity.umbc.edu/paper/html/id/476/Annotating-named-entities-in-Twitter-data-with-crowdsourcing</link>
  <description><![CDATA[We describe our experience using both Amazon Mechanical Turk (MTurk) and Crowd Flower to collect simple named entity annotations for Twitter status updates. Unlike most genres that have traditionally been the focus of named entity experiments, Twitter is far more informal and abbreviated. The collected annotations and annotation techniques will provide a first step toward the full study of named entity recognition in domains like Facebook and Twitter. We also briefly describe how to use MTurk...]]></description>
  <dc:date>2010-06-06</dc:date>
 </item>
</rdf:RDF>
